Fix MaxTripLegs constraint allowing infinite same-mode expansion #99
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Multimodal search was being killed by the system due to unbounded memory growth during frontier expansion.
Root Cause
The
MaxTripLegsconstraint inconstraint.rsincorrectly validated same-mode edge continuations:When
active_mode == edge_mode(continuing with the same travel mode), the code returnedn_legs = 0, making the constraint check always pass regardless of actual trip leg count. This allowed infinite expansion within a single mode once any mode transition exceeded the limit.Changes
_ => 0to_ => n_existing_legsto properly validate same-mode continuationstest_max_trip_legs_same_mode_continuation_at_limitto verify same-mode edges are rejected when over the limitThe constraint now correctly bounds search expansion for both mode transitions and same-mode continuations.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.